Can't run vanet-routing-compare.cc

[azra seyyedi]

Hello

I'm new to NS3. I studied vanet-routing-compare.cc script, but I'm getting confused with the results. I attached the photo which shows error messages.

I appreciate who can help me understand why this is happening and how I can solve it.

[Azra]

By using the gdb debugger, I get the following message. Can anyone help me to understand it?

The program being debugged has been started already.

Start it from the beginning? (y or n) y
Starting program: /home/azra/Desktop/ns-allinone-3.31/ns-3.31/build/scratch/vanet-routing-compare --scenario=1 --saveconfig=scenario1.txt
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
msg="Could not connect callback to /NodeList/*/DeviceList/*/ns3::WifiNetDevice/Phy/PhyTxDrop", file=../src/core/model/config.cc, line=920
terminate called without an active exception

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 }

[Ali Jan]

just debug/recompile the code or services

--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/664bc9c4-2bf7-4cb0-9307-e5bce20bab7an%40googlegroups.com.

[azra seyyedi]

Thanks alot for your reply.

Actually I did this, but finally I got this message. Can you please help me with some more details?

You received this message because you are subscribed to a topic in the Google Groups "ns-3-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ns-3-users/VWTV9ZdY7fs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ns-3-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/CACOjBGtusBPSvosvFmJEV-NvOmd7VMjMVE4ByR2VRJBetUr_qw%40mail.gmail.com.

[frank obinna]

please i have the same problem. how did you solve this

[Azra]

Unfortunately, I have not been able to solve it yet.

[Tom Henderson]

On 10/10/20 5:13 AM, frank obinna wrote:
> Hi
> I solved the problem by running an update on my Ubuntu. You can try that
> as well
>

You found a bug in that example program; I have filed an issue on it and
will try to fix it in ns-3-dev next week.

https://gitlab.com/nsnam/ns-3-dev/-/issues/275

Briefly, what is needed is as follows:

1) These trace lines are missing a dollar sign (syntax error) before the
ns3::WifiNetDevice:

- Config::Connect
("/NodeList/*/DeviceList/*/ns3::WifiNetDevice/Phy/PhyTxDrop",
MakeCallback (&WifiPhyStats::PhyTxDrop, m_wifiPhyStats));
- Config::Connect
("/NodeList/*/DeviceList/*/ns3::WifiNetDevice/Phy/PhyRxDrop",
MakeCallback (&WifiPhyStats::PhyRxDrop, m_wifiPhyStats));
+ Config::Connect
("/NodeList/*/DeviceList/*/$ns3::WifiNetDevice/Phy/PhyTxDrop",
MakeCallback (&WifiPhyStats::PhyTxDrop, m_wifiPhyStats));
+ Config::Connect
("/NodeList/*/DeviceList/*/$ns3::WifiNetDevice/Phy/PhyRxDrop",
MakeCallback (&WifiPhyStats::PhyRxDrop, m_wifiPhyStats));

2) the signature on the WififPhy::PhyRxDrop trace has recently changed:

void
-WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet)
+WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet,
WifiPhyRxfailureReason reason)


- Tom

[frank obinna]

THANK YOU sir for the reply, i got another error on trying to run your program

void
WifiPhyStats::PhyTxDrop (std::string context, Ptr<const Packet> packet)
{
  NS_LOG_UNCOND ("PHY Tx Drop");
}

void

WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet, WifiPhyRxfailureReason reason)

{
  NS_LOG_UNCOND ("PHY Rx Drop");

Config::Connect ("/NodeList/*/DeviceList/*/Phy/State/Tx", MakeCallback (&WifiPhyStats::PhyTxTrace, m_wifiPhyStats));
  // TxDrop, RxDrop not working yet.  Not sure what I'm doing wrong.

  Config::Connect ("/NodeList/*/DeviceList/*/$ns3::WifiNetDevice/Phy/PhyTxDrop", MakeCallback (&WifiPhyStats::PhyTxDrop, m_wifiPhyStats));

  Config::Connect ("/NodeList/*/DeviceList/*/$ns3::WifiNetDevice/Phy/PhyRxDrop", MakeCallback (&WifiPhyStats::PhyRxDrop, m_wifiPhyStats));

I GOT THIS ERROR AFTER RUNNING

obinna@obinna-X580VD:~/Desktop/ns-allinone-3.31/ns-3.31$ ./waf --run "scratch/vanet-routing-compare --protocol=1 --scenario=2"
Waf: Entering directory `/home/obinna/Desktop/ns-allinone-3.31/ns-3.31/build'
[2804/2857] Compiling scratch/vanet-routing-compare.cc
../scratch/vanet-routing-compare.cc:821:1: error: no declaration matches ‘void WifiPhyStats::PhyRxDrop(std::string, ns3::Ptr<const ns3::Packet>, ns3::WifiPhyRxfailureReason)’
  821 | WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet, WifiPhyRxfailureReason reason)
      | ^~~~~~~~~~~~
../scratch/vanet-routing-compare.cc:775:8: note: candidate is: ‘void WifiPhyStats::PhyRxDrop(std::string, ns3::Ptr<const ns3::Packet>)’
  775 |   void PhyRxDrop (std::string context, Ptr<const Packet> packet);
      |        ^~~~~~~~~
../scratch/vanet-routing-compare.cc:722:7: note: ‘class WifiPhyStats’ defined here
  722 | class WifiPhyStats : public Object
      |       ^~~~~~~~~~~~

Waf: Leaving directory `/home/obinna/Desktop/ns-allinone-3.31/ns-3.31/build'
Build failed
 -> task in 'vanet-routing-compare' failed with exit status 1 (run with -v to display more information)

I WILL REALLY APPRECIATE YOUR HELP, FOR WEEKS NOW I HAVE BEEN ON THIS SIMULATION

[Tom Henderson]

On 10/11/20 1:52 AM, frank obinna wrote:
> THANK YOU sir for the reply, i got another error on trying to run your
> program
>
> void
> WifiPhyStats::PhyTxDrop (std::string context, Ptr<const Packet> packet)
> {
>   NS_LOG_UNCOND ("PHY Tx Drop");
> }
>
> void
> WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet,
> WifiPhyRxfailureReason reason)

You need to add the 'reason' parameter both here and in the declaration
of this method; sorry I did not mention it earlier.

- Tom

[frank obinna]

thank you sir for the swift replies, sorry TOM, i am new with ns3, i dont know where the declaration is located on the code line.

//NS_LOG_UNCOND ("Received PHY size=" << pktSize);

}

void
WifiPhyStats::PhyTxDrop (std::string context, Ptr<const Packet> packet)
{
  NS_LOG_UNCOND ("PHY Tx Drop");
}

void

WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet,WifiPhyRxfailureReason reason)

{
  NS_LOG_UNCOND ("PHY Rx Drop");
}

thank you for your replies so far , i really appreciate your help

[Tom Henderson]

On 10/11/20 9:15 AM, frank obinna wrote:
> thank you sir for the swift replies, sorry TOM, i am new with ns3, i
> dont know where the declaration is located on the code line.

You will find it around line 775 of the program:

  /**
   * \brief Callback signiture for Phy/RxDrop
   * \param context this object
   * \param packet the rx packet being dropped
   * \return none
   */
  void PhyRxDrop (std::string context, Ptr<const Packet> packet);

- tom

[frank obinna]

thank you so much Tom, with a grateful heart i say thank you. it is running now, i spent a month trying to fix this bug

[Azra]

Thank you Tom. It was very helpful for me. Now this program is running after weeks.

I really appreciate your help.

[frank obinna]

hi Tom, hope you are doing great.

i was able to run simulation for protocol 1,2 and 3 with scenario 2"  but protocol 4 gave an error at the end of the simulation. please do you also have solution to this bug shown below?

At t=100s BSM_PDR1=0 BSM_PDR1=0 BSM_PDR3=0 BSM_PDR4=0 BSM_PDR5=0 BSM_PDR6=0 BSM_PDR7=0 BSM_PDR8=0 BSM_PDR9=0 BSM_PDR10=0 Goodput=0Kbps
--------Total Results of the simulation----------

Total sent packets  =0
Total Received Packets =0
Total Lost Packets =0

Packet Loss ratio =Command ['/home/obinna/Desktop/ns-allinone-3.31/ns-3.31/build/scratch/vanet-routing-compare', '--protocol=4', '--scenario=2'] terminated with signal SIGFPE. Run it under a debugger to get more information (./waf --run <program> --gdb").

thank you as i await your reply

[Tom Henderson]

On 10/14/20 8:02 AM, frank obinna wrote:

hi Tom, hope you are doing great.

i was able to run simulation for protocol 1,2 and 3 with scenario 2"  but protocol 4 gave an error at the end of the simulation. please do you also have solution to this bug shown below?

At t=100s BSM_PDR1=0 BSM_PDR1=0 BSM_PDR3=0 BSM_PDR4=0 BSM_PDR5=0 BSM_PDR6=0 BSM_PDR7=0 BSM_PDR8=0 BSM_PDR9=0 BSM_PDR10=0 Goodput=0Kbps
--------Total Results of the simulation----------

Total sent packets  =0
Total Received Packets =0
Total Lost Packets =0

Packet Loss ratio =Command ['/home/obinna/Desktop/ns-allinone-3.31/ns-3.31/build/scratch/vanet-routing-compare', '--protocol=4', '--scenario=2'] terminated with signal SIGFPE. Run it under a debugger to get more information (./waf --run <program> --gdb").

I just pushed a small patch to ns-3-dev to fix this issue.

https://gitlab.com/nsnam/ns-3-dev/-/commit/d9f4d1e0171dd3129cf38e793f1475e60290d611

- Tom

[Aman Verma]

sir, please help me in solving the following error

aman@aman:~/ns-allinone-3.32/ns-3.32$ ./waf --run scratch/vanet-routing-compare

Waf: Entering directory `/home/aman/ns-allinone-3.32/ns-3.32/build'

Waf: Leaving directory `/home/aman/ns-allinone-3.32/ns-3.32/build'

Build commands will be stored in build/compile_commands.json

'build' finished successfully (0.754s)

msg="Could not connect callback to /NodeList/*/DeviceList/*/ns3::WifiNetDevice/Phy/PhyTxDrop", +0.000000000s -1 file=../src/core/model/config.cc, line=923

terminate called without an active exception

Command ['/home/aman/ns-allinone-3.32/ns-3.32/build/scratch/vanet-routing-compare'] terminated with signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --gdb").

[frank obinna]

greetings, please can i run simulation of vanets on ns3 for ieee802.11bd, since this is more optimal than ieee 802.11p please i need an idea on how to change the parameters or which version of ns3 can help better in my simulation, i am currently running ns3.31. thank you as i await your response

[Ben Frey]

Hi Tom, first off thanks for your work on the ns-3 platform. Have spent quite a bit of time using it for undergraduate research in computational physics. 

Following up on this thread, not sure that these changes made it into ns-3.33, or the dev git (https://github.com/nsnam/ns-3-dev-git/tree/master/src/wave/examples) either. 

Thanks again,

Ben

[Tom Henderson]

Ben,
Inline below.

On 1/14/21 1:18 PM, Ben Frey wrote:
> Hi Tom, first off thanks for your work on the ns-3 platform. Have
> spent quite a bit of time using it for undergraduate research in
> computational physics.

Thanks, I am curious-- are you using ns-3 outside of the context of
networking (for physics), just as a general-purpose discrete-event
simulator, or was it for networking.

>
> Following up on this thread, not sure that these changes made it into
> ns-3.33, or the dev git
> (https://github.com/nsnam/ns-3-dev-git/tree/master/src/wave/examples)
> either.
>

You are correct; I forgot to return to this issue:

https://gitlab.com/nsnam/ns-3-dev/-/issues/275

I only fixed the DSR issue at that time.  Will try to close it shortly.

- Tom

[Ben Frey]

Tom, thanks for the quick response. 

I also have noticed some strange issues with dependency of "vanet-routing-compare.cc" on "src/core/model/global-value.cc".

Around line 1899 (and various other lines), "VRCcumulativeBsmCaptureStart" seems to depend on a new data type "TimeValue". My "global-value.cc" class was unable to cast this new type into a string. Reverting to the old type "UintegerValue" fixed the issue. I'm new to the ns-3 group despite having used the software, so I apologize for the informal pull.

>Thanks, I am curious-- are you using ns-3 outside of the context of
>networking (for physics), just as a general-purpose discrete-event
>simulator, or was it for networking.

Thanks for your interest. I'm working with one of my professors to publish a paper on a kinematic-based probabilistic dynamic transmission model to adapt the transmission rate of individual nodes that are deemed more "at-risk" of collision. Physics and Comp Sci. major but mainly using ns-3 within the context of networking. We've talked about playing around with the various physical layer propagation methods but are mainly focused on this new dynamic transmission method. 

Thanks again,

Ben

[Rima Benelmir]

@tom 

hello, can you help me to solve this error please :

msg="Could not connect callback to /NodeList/*/DeviceList/*/ns3::WifiNetDevice/Phy/PhyTxDrop", +0.000000000s -1 file=../../src/core/model/config.cc, line=923

terminate called without an active exception

Command ['/home/rima/Bureau/ns-allinone-3.32/ns-3.32/build/debug/scratch/vanet-routing-compare', '--protocol=1', '--scenario=2'] terminated with signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --gdb").

[Tom Henderson]

On 1/14/21 4:55 PM, Rima Benelmir wrote:
>
> @tom
> hello, can you help me to solve this error please :
> msg="Could not connect callback to
> /NodeList/*/DeviceList/*/ns3::WifiNetDevice/Phy/PhyTxDrop",
> +0.000000000s -1 file=../../src/core/model/config.cc, line=923
> terminate called without an active exception
> Command
> ['/home/rima/Bureau/ns-allinone-3.32/ns-3.32/build/debug/scratch/vanet-routing-compare',
> '--protocol=1', '--scenario=2'] terminated with signal SIGIOT. Run it
> under a debugger to get more information (./waf --run <program> --gdb").

Please see my response in this message, earlier in this thread.

https://groups.google.com/g/ns-3-users/c/VWTV9ZdY7fs/m/7zoe-P8cAQAJ

I will try to fix it in ns-3-dev shortly.

- Tom

[Nadine]

I've done the modification but I'm getting in the output this result, is it correct? And I'm getting the same in AODV protocol.

OLSR 9.93261 6 received one packet from 10.1.0.17

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

PHY Rx Drop

BSM_PDR1=0.951588 BSM_PDR2=0.79233 BSM_PDR3=0.49083 BSM_PDR4=0.307493 BSM_PDR5=0.214733 BSM_PDR6=0.176024 BSM_PDR7=0.150939 BSM_PDR8=0.150939 BSM_PDR9=0.150939 BSM_PDR10=0.150939 Goodput=1.5872Kbps MAC/PHY-oh=0.262021  

[Tom Henderson]

It is what I get also, but whether it is correct or not, I am not sure. 
This code was contributed by an author who is no longer working on the
project, and we haven't had a volunteer for this module for at least
five years now.  If someone would like to go through the output of this
program and let us know if they believe it to be correct, we can update
some documentation regarding it. Otherwise, you will have to check the
code and results for yourself.

- Tom

[Shilpi Mittal]

Hey team members,

Any one can help me out in SUMO installation as it is returning bugs.

Kindly reply

Seek for your support.

--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/705e83ba-47ee-8708-141c-376d4c5599c9%40tomh.org.

[rui liu]

Hi all I am using ns 3.32 now. I used to meet the same problem. Based on the guidance in this forum, I updates the code to this code (fixed by Tom). 

Then that's what I got:

assert failed. cond="uid <= m_information.size () && uid != 0", +0.000000000s -1 file=../src/core/model/type-id.cc, line=462

libc++abi.dylib: terminating

Does anyone have the same error with me?

or maybe I lost something should also be updated?

Thanks!

[vibha oberoi]

Hi ,

Have you sorted your installation issues or still facing the issue?

Thanks 

Vibha Oberoi

To view this discussion on the web visit https://groups.google.com/d/msgid/ns-3-users/CADeTpUfR%3DtoV3tDFzJq%3Dm66062bwP7-g8vdi0agEmzyS76okpQ%40mail.gmail.com.

--

Inline image

[Juan Antonio Arízaga Silva]

THe best workaround is to download the  examples from here https://gitlab.com/nsnam/ns-3-dev/-/tree/726199c94ef4848086b370d3c11bee020e86278b/src/wave/examples

They are in the development branch. 

Best regards

[Juan Antonio Arízaga Silva]

Including the reason into the code:

void

WifiPhyStats::PhyRxDrop (std::string context, Ptr<const Packet> packet, WifiPhyRxfailureReason reason)

{

  NS_LOG_UNCOND ("PHY Rx Drop");NS_LOG_UNCOND("this " << reason);

}

give at least 3 different causes to drop :

busy decoding preamble

L_SIG_FAILURE 

and RXING